-
Notifications
You must be signed in to change notification settings - Fork 985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#18934] universal scanner in wallet receive #19409
Conversation
Adding |
Jenkins Builds
|
(seq time-frame-to-string)) | ||
[custom-time-frame time-frame-to-string])] | ||
[rn/view {:style style/row-centered} | ||
(when (seq time-frame-string) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's better to use string/blank?
to check for string emptiness.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just refactored this code to remove the unnecessary :<>
there.
But I agree, I'll update it, to improve the whole piece of code 👍 thanks for spotting it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @ibrkhalil
I checked the implementation, and I'd prefer keep it as is since it's a bit complex, it's not just about checking a string.
the component receives:
time-frame
, time-frame-string
and time-frame-to-string
.
then it shadows
time-frame-string
with (time-string time-frame time-frame-string)
and sometimes time-frame-string
will take the value of the received time-frame-string
, so I guess the decision to use seq
was because it's more general.
Since it's a bit hard to track all the flow to make sure this won't create a bug in some cases, I'd prefer to keep it as is, additionally, the seq
is being used in a translation string, so it won't be ""
or " "
.
would be nice to have a video or photo attached in the pr description 👍 |
92% of end-end tests have passed
Failed tests (3)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUiTwo:
Expected to fail tests (1)Click to expandClass TestCommunityOneDeviceMerged:
Passed tests (44)Click to expandClass TestCommunityMultipleDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestGroupChatMultipleDeviceMergedNewUI:
Class TestActivityMultipleDevicePRTwo:
Class TestDeepLinksOneDevice:
Class TestCommunityMultipleDeviceMergedTwo:
Class TestActivityMultipleDevicePR:
Class TestCommunityOneDeviceMerged:
Class TestActivityCenterContactRequestMultipleDevicePR:
|
100% of end-end tests have passed
Passed tests (3)Click to expandClass TestOneToOneChatMultipleSharedDevicesNewUiTwo:
|
Hi @ulisesmac. Thank you for PR. Ready to be merged |
@ulisesmac ready to be merged and cherrypicked. cc @cammellos |
e5dd184
to
b68e76d
Compare
fixes #18934
fixes #19411
Summary
This PR mounts the universal QR code scanner in the wallet receive modal although correct redirections are not complete yet.
Additionally this PR solves some other small bugs:
:yinYang
).:wallet-accounts
instead of:wallet.accounts
(dot separated).Review notes
Although scanning seems useless atm, the QR code scanner is properly dispatched, please take it into consideration while testing.
Platforms
Steps to test
status: ready